Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Important! Template update for nf-core/tools v2.13 #380

Merged
merged 5 commits into from
Feb 28, 2024

Conversation

nf-core-bot
Copy link
Member

Version 2.13 of nf-core/tools has just been released with updates to the nf-core template. This automated pull-request attempts to apply the relevant updates to this pipeline.

Please make sure to merge this pull-request as soon as possible, resolving any merge conflicts in the nf-core-template-merge-2.13 branch (or your own fork, if you prefer). Once complete, make a new minor release of your pipeline.

For instructions on how to merge this PR, please see https://nf-co.re/docs/contributing/sync/.

For more information about this release of nf-core/tools, please see the v2.13 release page.

@nf-core-bot nf-core-bot requested a review from a team as a code owner February 20, 2024 15:29
@edmundmiller edmundmiller self-assigned this Feb 23, 2024
Copy link

github-actions bot commented Feb 23, 2024

nf-core lint overall result: Passed ✅

Posted for pipeline commit 664ff42

+| ✅ 175 tests passed       |+
#| ❔   5 tests were ignored |#

❔ Tests ignored:

✅ Tests passed:

Run details

  • nf-core/tools version 2.13
  • Run at 2024-02-28 19:02:07

Copy link

@CarsonJM CarsonJM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Several comments! Mainly because I am now second guessing how I handled the template merge in phageannotator and mag haha

assets/schema_input.json Show resolved Hide resolved
conf/modules.config Show resolved Hide resolved
@@ -17,7 +17,7 @@ jobs:
aligner: ["bismark", "bismark_hisat", "bwameth"]
steps:
- name: Launch workflow via tower
uses: seqeralabs/action-tower-launch@v2
uses: seqeralabs/action-tower-launch@922e5c8d5ac4e918107ec311d2ebbd65e5982b3d # v2

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this one work now?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Schrödinger's action 🤷🏻‍♂️

.groupTuple()
.map {
meta, fastq ->
def meta_clone = meta.clone()

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you not just replace the id?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know, honestly. I think there's a section in the advanced training on this. @sateeshperi just updated it in #381.

As I said above, I think we need to turn this into a subworkflow.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's right - see bytesize by Rob Syme about workflow safety & immutable objects tl;dr - never modify meta maps in place

Copy link

@CarsonJM CarsonJM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I'm going to have to steal some of these changes you made 😅

@edmundmiller edmundmiller merged commit 3b5356d into dev Feb 28, 2024
32 checks passed
@sateeshperi sateeshperi deleted the nf-core-template-merge-2.13 branch February 29, 2024 03:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants